home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1994 March
/
Internet Info CD-ROM (Walnut Creek) (March 1994).iso
/
inet
/
internet-drafts
/
draft-houttuin-rfc1327-tutor-04.txt
< prev
next >
Wrap
Text File
|
1993-09-23
|
2KB
|
63 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1506:
RTR 6:
Title: A Tutorial on Gatewaying between X.400 and
Internet Mail
Author: J. Houttuin
Mailbox: houttuin@rare.nl
Pages: 39
Characters: 85,550
Updates/Obsoletes: none
There are many ways in which X.400 and Internet (STD 11, RFC 822) mail
systems can be interconnected. Addresses and service elements can be
mapped onto each other in different ways. From the early available
gateway implementations, one was not necessarily better than another,
but the sole fact that each handled the mappings in a different way
led to major interworking problems, especially when a message (or
address) crossed more than one gateway. The need for one global
standard on how to implement X.400 - Internet mail gatewaying was
satisfied by the Internet Request For Comments 1327, titled "Mapping
between X.400(1988)/ISO 10021 and RFC 822." This tutorial was
produced especially to help new gateway managers find their way into
the complicated subject of mail gatewaying according to RFC 1327.
This memo provides information for the Internet community. It does
not specify an Internet standard. Distribution of this memo is
unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body
"help: ways_to_get_rfcs". For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1111, "Instructions to RFC
Authors", for further information.
Joyce K. Reynolds
USC/Information Sciences Institute